Managing input/output interruptions in non-dedicated interruption hardware environments

ABSTRACT

Input/output interruptions are managed in computing environments that do not use dedicated per-guest interruption hardware to present interruptions. Dispatchable guest programs in the environment receive I/O interruptions directly without hypervisor intervention. This is facilitated by using one or more interruption controls stored in memory and associated with each guest program. For those guest programs that are not currently dispatchable, interruptions can be posted for the guests and notifications to the hypervisor can be aggregated. The hypervisor can then process a plurality of notifications for the plurality of guests in a single invocation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. patent application Ser. No. 10/435,907, filed May 12, 2003, entitled “MANAGING INPUT/OUTPUT INTERRUPTIONS IN NON-DEDICATED INTERRUPTION HARDWARE ENVIRONMENTS”, Belmar et al., the entirety of which is hereby incorporated herein by reference.

FIELD OF THE INVENTION

This invention relates, in general, to managing input/output (I/O) interruptions, and in particular, to managing I/O interruptions in environments that present I/O interruptions to guests without using per-guest interruption hardware.

BACKGROUND OF THE INVENTION

As computing environments increase in the number of guests that they service, it is difficult to have interruption hardware dedicated to each guest. For example, in virtualized real memory environments, such as those based on the z/VM virtual machine support, offered by International Business Machines Corporation, Armonk, N.Y., a large number of low utilization guest operating systems are capable of being serviced. Typically, a virtual machine hypervisor controls the interactions between the guest operating systems and the physical resources. The physical resources are owned by the hypervisor, and the hypervisor dispatches the resources as needed to meet the guest operating systems' processing demands. The hypervisor is used in this manner, since the large number of guests (e.g., hundreds or thousands) that are possible precludes the hypervisor from simply partitioning and assigning the hardware resources to the configured guests, as with other types of virtualization, such as with logical partitioning.

In addition to dispatching responsibilities, the hypervisor has many other responsibilities, including managing I/O interruptions for the guest operating systems. When an I/O interruption targets a guest operating system, the hypervisor takes control because there are insufficient native hardware controls to allow each of the possible many virtual machines to be assigned its own unique set of interruption controls. Thus, in response to an I/O interruption, such as an adapter interruption, a condition is recognized which causes the hypervisor to gain control. The hypervisor then examines the VM-owned adapter state indicators to identify the signaling device, correlates that device to the owning guest, posts the guest-owned state indicator, and makes a virtual adapter interruption pending to the associated guest operating system. This interruption interception and subsequent interruption processing overhead is significant, and with the increasing number of guest operating systems that can be processed, the overhead associated with using the hypervisor for such adapter interruptions is becoming prohibitive.

Based on the foregoing, a need exists for an enhanced capability to handle I/O interruptions. For example, a need exists for a technique that minimizes hypervisor involvement in managing I/O interruptions.

SUMMARY OF THE INVENTION

The shortcomings of the prior art are overcome and additional advantages are provided through the provision of a method of managing I/O interruptions. The method includes, for instance, having a dispatchable guest program in a computing environment, the computing environment to present I/O interruptions absent per-guest interruption hardware; and providing an I/O interruption to the dispatchable guest program, absent intervention by a hypervisor of the computing environment.

In a further aspect of the present invention, a method of managing I/O interruptions is provided. The method includes, for instance, aggregating in a list a plurality of notifications for a plurality of guest programs of a computing environment for which a plurality of I/O interruptions are to be presented; and providing the list to a hypervisor of the computing environment, the hypervisor to process at least one notification of the plurality of notifications.

In another aspect of the present invention, a method of managing I/O interruptions is provided. The method includes, for instance, obtaining an I/O interruption for a guest program of a virtualized real memory environment; determining a dispatch state of the guest program; providing the I/O interruption to the guest program absent intervention by a hypervisor of the virtualized real memory environment, in response to the dispatch state being of one state; and providing the I/O interruption to the guest program with hypervisor intervention, in response to the dispatch state being of another state.

In yet a further aspect of the present invention, a method of managing I/O interruptions is provided. The method includes, for instance, providing an I/O interruption to a dispatchable guest program of a virtualized real memory environment, wherein the providing is absent of intervention by a hypervisor of the virtualized real memory environment.

System and computer program products corresponding to the above-summarized methods are also described and claimed herein.

Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

FIG. 1 depicts one embodiment of a computing environment to incorporate and use one or more aspects of the present invention;

FIG. 2 depicts one example of a guest interruption state area for a guest operating system of FIG. 1, in accordance with an aspect of the present invention;

FIG. 3 depicts one embodiment of the logic associated with receiving an I/O interruption, in accordance with an aspect of the present invention;

FIGS. 4 a-4 b depict one embodiment of details associated with posting a received I/O interruption, in accordance with an aspect of the present invention; and

FIG. 5 depicts one embodiment of the logic associated with presenting a posted I/O interruption, in accordance with an aspect of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

In accordance with an aspect of the present invention, an I/O interruption capability is provided in which hypervisor involvement in managing I/O interruptions is minimized. For example, in non-dedicated interruption hardware environments, I/O interruptions, such as adapter interruptions, are presented directly to guest programs (e.g., guest operating systems) which are dispatched or due to be dispatched (i.e., dispatchable) without requiring any hypervisor involvement. As a further example, for guests not due to be dispatched (i.e., non-dispatchable), interruptions can be posted for the guests, and notifications to the hypervisor can be aggregated, such that a single invocation of the hypervisor can process a plurality of notifications for a plurality of guest programs.

One embodiment of a computing environment to incorporate and use one or more aspects of the present invention is described with reference to FIG. 1. Computing environment 100 is based, for instance, on the z/Architecture offered by International Business Machines Corporation, Armonk, N.Y. The z/Architecture is described in an IBM® publication entitled, “z/Architecture Principles of Operation,” IBM® Publication No. SA-22-7832-00, December 2000, which is hereby incorporated herein by reference in its entirety. (IBM® is a registered trademark of International Business Machines Corporation, Armonk, N.Y., USA. Other names used herein may be registered trademarks, trademarks, or product names of International Business Machines Corporation or other companies.) In one example, a computing environment based on the z/Architecture includes an eServer zSeries, offered by International Business Machines Corporation, Armonk, N.Y.

As one example, computing environment 100 includes a central processor complex (CPC) 102 providing virtual machine support. CPC 102 includes, for instance, one or more virtual machines 104, one or more central processors 106, at least one hypervisor 108 (e.g., a control program), and an input/output subsystem 110, each of which is described below.

The virtual machine support of the CPC provides the ability to operate large numbers of virtual machines, each capable of hosting a guest operating system 112, such as Linux. Each virtual machine 104 is capable of functioning as a separate system. That is, each virtual machine can be independently reset, host a guest operating system, and operate with different programs. An operating system or application program running in a virtual machine appears to have access to a full and complete system, but in reality, only a portion of it is available.

In this particular example, the model of virtual machines is a V=V model, in which the memory of a virtual machine is backed by virtual memory, instead of real memory. Each virtual machine has a virtual linear memory space. The physical resources are owned by a hypervisor 108, such as a VM hypervisor, and the shared physical resources are dispatched by the hypervisor to the guest operating systems, as needed, to meet their processing demands. This V=V virtual machine model assumes that the interactions between the guest operating systems and the physical shared machine resources are controlled by the VM hypervisor, since the large number of guests typically precludes the hypervisor from simply partitioning and assigning the hardware resources to the configured guests. One or more aspects of a V=V model are further described in an IBM publication entitled “z/VM: Running Guest Operating Systems,” IBM Publication No. SC24-5997-02, October 2001, which is hereby incorporated herein by reference in its entirety.

Central processors 106 are physical processor resources that are assignable to a virtual machine. For instance, virtual machine 104 includes one or more logical processors, each of which represents all or a share of a physical processor resource 106 that may by dynamically allocated to the virtual machine. Virtual machines 104 are managed by hypervisor 108. As examples, the hypervisor may be implemented in microcode running on processors 106 or be a part of a host operating system executing on the machine. In one example, hypervisor 108 is a VM hypervisor, such as z/VM®, offered by International Business Machines Corporation, Armonk, N.Y. One embodiment of z/VM® is described in an IBM publication entitled “z/VM: General Information Manual,” IBM Publication No. GC24-5991-04, October 2001, which is hereby incorporated herein by reference in its entirety.

Input/output subsystem 110 directs the flow of information between input devices and main storage. It is coupled to the central processing complex, in that it can be part of the central processing complex or separate therefrom. The I/O subsystem relieves the central processors of the task of communicating directly with the I/O devices coupled to the CPC and permits data processing to proceed concurrently with I/O processing. The I/O subsystem includes I/O communications adapters, such as QDIO adapters, infiniband adapters, etc., used in communicating with the I/O devices.

At times, the I/O subsystem produces interruptions that are to be presented to the guest operating systems of the virtual machines. In one example, these interruptions include adapter interruptions. Adapter interruptions have no associated status information (i.e., no other information apart from the interrupt initiative), but allow a device to initiate a program response to a device operation. An adapter interruption (or other I/O interruption) may be presented directly to a guest without hypervisor intervention, in accordance with an aspect of the present invention. For example, an adapter interruption for a dispatchable guest operating system is provided to the guest operating system without hypervisor intervention. The CPC (e.g., firmware or microcode) is able to present the interruption without knowledge or care of the hypervisor. To facilitate this, the CPC employs one or more controls associated with the guest, as described in further detail below.

Associated with each guest is a small amount of memory to maintain interruption virtualization and control information dedicated to that guest. As one example, the controls are provided in a contiguous block of storage, referred to herein as a guest interruption state area (GISA). One GISA is established for and is dedicated to each guest, and may be updated by the CPC directly without hypervisor intervention, or by the hypervisor for certain situations.

One example of a GISA is described with reference to FIG. 2. A GISA 200 is aligned on a quad-word boundary, as one example, and includes, for instance, the following:

(a) Alert list next address 202 which points to the next GISA in an alert list. An alert list is a linked list of GISAs, each corresponding to a guest for which there is at least one pending alerting condition. The alert list enables aggregation of interruptions for a plurality of guests, if such a situation warrants aggregation. If this GISA is the last in the alert list, then address 202 is zero. If the GISA is not in the alert list, then the address points to the GISA itself.

(b) Interruption pending mask (IPM) 204 is a mask associated with the guest that includes indicators for a plurality of interruption subclasses (ISCs) associated with the guest. As one example, the zSeries architecture provides added granularity of control of I/O interruptions by providing eight I/O interruption subclasses which are maskable via, for instance, Control Register 6. Each interruption subclass (ISC) controls the enablement of that subclass of I/O interrupt. There is a one for one correspondence between the bits of the IPM and the interruption subclasses in the guest's control register 6. When an adapter interruption is made pending for a guest, the bit in the IPM that corresponds to the ISC associated with the device presenting the interruption is set to one by the CPC. A bit in the IPM is reset (no adapter interruption pending state), when the corresponding interruption is presented to the guest; withdrawn by the host program; or reset.

c) Interruption Alert Mask (IAM) 206 is another mask corresponding to a guest. In one example, each bit in this mask also corresponds one for one with the eight I/O interruption subclass enablement bits located in the guest's control register 6. This mask is set by the hypervisor, when the hypervisor is to be notified (called an alert-interruption condition or alerting condition) that adapter interrupts on certain guest interruption subclasses are to be presented to the guest program. For example, when a guest program is in the wait state (i.e., non-dispatchable) and thus, the hypervisor does not have initiative to dispatch the guest program, the hypervisor is to be notified (via the alert interruption condition) of an adapter interruption pending condition for the guest in the wait state. The alert interruption provides initiative for the hypervisor to be given control so that it can then schedule the guest program to be dispatched. As described in further detail below, when a bit in the IAM is set, and an adapter interruption corresponding to the same guest interruption subclass is to be made pending, an alerting condition is created. After the alerting condition is recognized, the IAM is reset. This is an example of a case where the alert list is used to keep track of the list of guest programs for which the hypervisor is to process interruptions.

The GISA facilitates the presenting of adapter interruptions to the guest programs. Depending on the state of the guest program, the adapter interruption is presented directly to the guest program without hypervisor intervention, or some hypervisor involvement is used so that pending interruptions are presented timely. This is described in further detail with reference to FIGS. 3-5.

FIG. 3 depicts one embodiment of the logic associated with receiving an interruption for a guest, in accordance with an aspect of the present invention; FIGS. 4 a-4 b provide one embodiment of further details regarding the posting of a received I/O interruption; and FIG. 5 depicts one embodiment of the logic associated with presenting a posted interruption to an active guest.

Referring to FIG. 3, the central processing complex receives an interrupt, such as an adapter interrupt, from the I/O subsystem via, for instance, hardware generated signals, STEP 300. In response to receiving the interrupt, the CPC sets one or more interrupt indicators, STEP 302. In one example, this includes setting an IPM bit associated with the guest to which the interrupt is to be presented. Moreover, the CPC performs various actions to determine whether the hypervisor is to be alerted to an interruption condition, STEP 304. These actions, as well as setting the indicator, are described further with reference to FIGS. 4 a-4 b.

Referring to FIG. 4 a, in response to an interruption being received by the CPC, the IPM and IAM are fetched from the GISA and two copies (e.g., Copy A and Copy B) are kept in, for instance, a work area in main memory, STEP 400. Thereafter, the IPM bit in Copy A corresponding to N, where N is the ISC number for the interruption to be posted, is set to, for instance, one, STEP 402. A determination is also made as to whether the corresponding IAM bit is currently set, INQUIRY 404.

If the IAM bit is set, indicating that the hypervisor is to be alerted, then the IAM is reset, STEP 406. In one example, this includes setting the entire IAM to zeros. Moreover, a determination is made as to whether an alert is already pending for this guest, INQUIRY 408. If the alert list next address (Naddr) in the GISA points to itself indicating that the alert is not already pending, then the GISA is inserted into the alert list, as follows. A determination is made as to whether the IPM and IAM of Copy B equal the IPM and IAM of the GISA and whether the alert is still not pending for this GISA, INQUIRY 410. If the compare is successful, then the alert list next address in the GISA is set to zeros, and the IPM and IAM of the GISA are set to Copy A, STEP 412 (FIG. 4 b). In one example, INQUIRY 410 and STEP 412 are accomplished by an atomic compare double and swap operation. Next, the Naddr in the GISA is set to the contents of an alert list origin (ALO) stored in, for instance, a global control block, STEP 414. Moreover, a determination is made as to whether the ALO and the Naddr value just placed in the GISA are equal, INQUIRY 416. If unequal, processing continues with STEP 414. Otherwise, the address of the GISA is swapped into the ALO, STEP 418 and, an alerting interrupt initiative is generated for the hypervisor, STEP 420. In one example, the check of INQUIRY 416 and the swap of STEP 418 are performed by an atomic compare and swap operation.

The alerting interruption is either made pending or suppressed for a period of time (e.g., as preset by the hypervisor) allowing alerts to aggregate for the hypervisor. In response to accepting by the hypervisor the alerting interruption from the CPC, the alert list is examined and the corresponding guests are serviced by the hypervisor. The hypervisor can aggregate the processing of multiple pending interruptions for multiple guests during a single hypervisor invocation, instead of having to be dispatched to process each request individually. This processing includes removing the affected guests from the wait state and placing them on the dispatch queue.

When the hypervisor processes the alert list, it first performs a compare and swap operation to atomically retrieve the alert list origin and place zeros in the alert list origin. By doing so, a new alert list is subsequently created for the CPC causing the hypervisor's fetching of the alert list to appear atomic. Since the hypervisor and the CPC can update the fields in the GISA concurrently, when the hypervisor processes the GISA for alerting interruptions, it dequeues the GISA from the alert list first (e.g., sets the alert list next address to point to the GISA itself), before again making the IAM non-zero. By doing so, the hypervisor ensures that no alert interruption condition is lost.

Returning to INQUIRY 410 (FIG. 4 a), if the IPM and IAM in the GISA are not equal to the IPM and IAM in Copy B, then processing continues with STEP 400. Further, returning to INQUIRY 404, if the IAM bit in Copy A is not one or if the GISA is already a part of the alert list (the alert list next address does not point to itself), INQUIRY 408, then a determination is made as to whether the IPM and IAM in the GISA are equal to the IPM and IAM in Copy B, INQUIRY 422. In one embodiment, this determination is made by a compare and swap operation. For example, the compare and swap instruction atomically compares Copy B with the appropriate portions of the GISA. If they are unequal, processing continues with STEP 400. Otherwise, the IPM and IAM of the GISA are set to the IPM and IAM of Copy A, STEP 424.

Since the guest is active (e.g., IAM is zero), the adapter interruption is presented to the guest without hypervisor intervention. This is described further with reference to FIG. 5. In one example, when the guest is active, IPM bits in the GISA corresponding to the guest are examined periodically to determine whether there is a pending interruption for that guest, STEP 500. If there is no interruption pending for the guest, then processing continues at STEP 500. Otherwise, if there is a pending interruption, then the IPM bit is turned off, for example, for the highest priority enabled ISC, STEP 504. Additionally, the adapter interruption is presented to the guest for this ISC, STEP 506. In one example, this is performed by storing the current program status word (PSW) and I/O interruption code in guest memory, and loading a new PSW from guest memory to give control to the interruption handler in the guest program.

In the case where a guest program is dispatchable but not active, the interruption is presented in the manner above when the guest becomes active.

Described in detail above is a capability for providing interrupts to guests which minimizes hypervisor involvement. The capability is facilitated by a memory mapped virtualization technique in which interruption hardware is virtualized. This capability can be used for any hardware that generates stateless interruptions (e.g., does not carry other information apart from the interruption). Advantageously, one or more aspects of this capability significantly reduce the processing overhead involved with presenting adapter interruptions to pageable mode guest operating systems, as well as other guest operating systems.

In one example, one or more aspects of the present invention can be included as part of an adapter interruption facility. One example of such a facility, without the extensions of the present invention, is included in eServer zSeries 900 servers, offered by International Business Machines Corporation, Armonk, N.Y. Further, information regarding one or more aspects of the facility is described in “zSeries Features For Optimized Sockets-Based Messaging: HiperSockets and OSA-Express,” by M. E. Baskey et al., which is hereby incorporated herein by reference in its entirety.

With such a facility, the interruption initiative presented to the hypervisor may be facilitated by employing a global summary provided by the facility. A program can use one or more instructions to test the state of a global summary indicator, or set or reset the indicator. Further, the time intervals for providing alerting interruptions to the hypervisor can be calculated according to a time delay technique that uses an adapter time delay value and adapter current time value of the facility.

As a further example, the starting address of the GISA for a particular guest is provided by the hypervisor to the CPC when a guest is made active. Additionally, the address of the owning guest's GISA for a particular device is provided by a system configuration command. Therefore, the address of the GISA uniquely identifies its associated guest and correlates that guest with the devices it owns. Yet further, the ALO is maintained in a global control block, referred to as a guest information block (GIB).

Although a computing environment is described above, one or more variations of the environment may be made without departing from the spirit of the present invention. For example, the CPC may include one or more logical partitions in which one or more virtual machines are residing therein. Further, if one or more logical partitions are provided, then an LPAR hypervisor may also be provided. Additionally, one or more CPCs an be provided.

Further, even though one or more aspects of the present invention are described with reference to a virtualized real memory environment, one or more aspects of the present invention are applicable to other environments that do not have or use per-guest interruption hardware.

Moreover, although examples of controls are provided herein, one or more other controls may be used and/or one or more modifications to one or more of the controls (e.g., different number of bits, etc.) may be made without departing from the spirit of the present invention.

Further, other variations to the described logic can be made without departing from the spirit of the present invention. For example, in another embodiment, alerts are aggregated by generating the altering interruption to the hypervisor only when the alert list transitions from empty to non-empty. Since the hypervisor processes the entire alert list in response to an alerting interruption, this technique avoids redundant alerting interruptions for which no additional hypervisor processing is necessary.

Yet further, although the guests in the examples provided herein are operating systems, other guests may benefit from one or more aspects of the present invention. Additionally, other than adapter interruptions can be managed in accordance with one or more aspects of the present invention.

The present invention can be included in an article of manufacture (e.g., one or more computer program products) having, for instance, computer usable media. The media has therein, for instance, computer readable program code means or logic (e.g., instructions, code, commands, etc.) to provide and facilitate the capabilities of the present invention. The article of manufacture can be included as a part of a computer system or sold separately.

Additionally, at least one program storage device readable by a machine embodying at least one program of instructions executable by the machine to perform the capabilities of the present invention can be provided.

The flow diagrams depicted herein are just examples. There may be many variations to these diagrams or the steps (or operations) described therein without departing from the spirit of the invention. For instance, the steps may be performed in a differing order, or steps may be added, deleted or modified. All of these variations are considered a part of the claimed invention.

Although preferred embodiments have been depicted and described in detail herein, it will be apparent to those skilled in the relevant art that various modifications, additions, substitutions and the like can be made without departing from the spirit of the invention and these are therefore considered to be within the scope of the invention as defined in the following claims. 

1. A method of managing input/output (I/O) interruptions, said method comprising: aggregating in a list a plurality of notifications for a plurality of guest programs of a computing environment for which a plurality of I/O interruptions are to be presented; and providing the list to a hypervisor of the computing environment, the hypervisor to process at least one notification of the plurality of notifications.
 2. The method of claim 1, further comprising processing, by the hypervisor, at least a multiple of notifications of the plurality of notifications corresponding to at least a multiple of guest programs of the plurality of guest programs.
 3. The method of claim 2, wherein the processing is performed via a single invocation of the hypervisor.
 4. The method of claim 2, wherein the at least a multiple of guest programs are in a non-dispatchable state, and the processing comprises placing the at least a multiple of guest programs in a dispatchable state.
 5. The method of claim 4, further comprising, for a guest program in the dispatchable state, presenting an I/O interruption to the guest program in response to the guest program becoming active.
 6. The method of claim 1, further comprising detecting the plurality of I/O interruptions, said detecting of an I/O interruption of the plurality of I/O interruptions comprising employing one or more controls associated with a guest program corresponding to the I/O interruption.
 7. The method of claim 1, wherein the aggregating is in response to a plurality of dispatch states of the plurality of guest programs.
 8. The method of claim 1, wherein the aggregating for a notification in the list comprises adding the notification to the list responsive to an indication by the hypervisor specifying involvement in processing an I/O interruption associated with that notification.
 9. The method of claim 8, wherein the indication is provided in a control associated with a guest program corresponding to the I/O interruption.
 10. A system of managing input/output (I/O) interruptions, said system comprising: means for aggregating in a list a plurality of notifications for a plurality of guest programs of a computing environment for which a plurality of I/O interruptions are to be presented; and means for providing the list to a hypervisor of the computing environment, the hypervisor to process at least one notification of the plurality of I/O notifications.
 11. The system of claim 10, further comprising means for processing, by the hypervisor, at least a multiple of notifications of the plurality of notifications corresponding to at least a multiple of guest programs of the plurality of guest programs.
 12. The system of claim 11, wherein the means for processing by the hypervisor comprises a single invocation of the hypervisor.
 13. The system of claim 11, wherein the at least a multiple of guest programs are in a non-dispatchable state, and the means for processing comprises means for placing the at least a multiple of guest programs in a dispatchable state.
 14. The system of claim 10, further comprising means for detecting the plurality of I/O interruptions, said means for detecting an I/O interruption of the plurality of I/O interruptions comprising means for employing one or more controls associated with a guest program corresponding to the I/O interruption.
 15. The system of claim 10, wherein the aggregating is in response to a plurality of dispatch states of the plurality of guest programs.
 16. The system of claim 10, wherein the means for aggregating for a notification in the list comprises means for adding the notification to the list responsive to an indication by the hypervisor specifying involvement in processing an I/O interruption associated with that notification.
 17. The system of claim 16, wherein the indication is provided in a control associated with a guest program corresponding to the I/O interruption.
 18. A system of managing input/output (I/O) interruptions, said system comprising: an aggregated list of a plurality of notifications for a plurality of guest programs of a computing environment for which a plurality of I/O interruptions are to be presented; and a hypervisor of the computing environment to process at least one notification of the plurality of notifications of the list.
 19. An article of manufacture comprising: at least one computer usable medium having computer readable program code logic to manage input/output (I/O) interruptions, the computer readable program code logic comprising: logic to provide an I/O interruption to a dispatchable guest program in a computing environment, said computing environment to present I/O interruptions absent per-guest interruption hardware, wherein the logic to provide comprises logic to provide the I/O interruption absent intervention by a hypervisor of the computing environment, and wherein the guest program is dispatchable and not active, and the logic to provide comprises logic to present the I/O interruption to the guest program, in response to the guest program becoming active.
 20. The article of manufacture of claim 19, wherein the logic to provide comprises logic to detect that the I/O interruption is pending for the guest program, the logic to detect employing one or more controls associated with the guest program.
 21. The article of manufacture of claim 20, wherein the detection is in response to a dispatch state of the guest program.
 22. The article of manufacture of claim 21, wherein the dispatch state becomes active, and the logic to provide comprises logic to present the I/O interruption to the guest program in response to detection of the I/O interruption for the active guest program.
 23. An article of manufacture comprising: at least one computer usable medium having computer readable program code logic to manage input/output (I/O) interruptions, the computer readable program code logic comprising: logic to aggregate in a list a plurality of notifications for a plurality of guest programs of a computing environment for which a plurality of I/O interruptions are to be presented; and logic to provide the list to a hypervisor of the computing environment, the hypervisor to process at least one notification of the plurality of notifications.
 24. The article of manufacture of claim 23, further comprising logic to process, by the hypervisor, at least a multiple of notifications of the plurality of notifications corresponding to at least a multiple of guest programs of the plurality of guest programs.
 25. The article of manufacture of claim 24, wherein there is a single invocation of the hypervisor.
 26. The article of manufacture of claim 24, wherein the at least a multiple of guest programs are in a non-dispatchable state, and the logic to process comprises logic to place the at least a multiple of guest programs in a dispatchable state.
 27. The article of manufacture of claim 23, further comprising logic to detect the plurality of I/O interruptions, said logic to detect an I/O interruption of the plurality of I/O interruptions comprising logic to employ one or more controls associated with a guest program corresponding to the I/O interruption.
 29. The article of manufacture of claim 23, wherein the aggregation is in response to a plurality of dispatch states of the plurality of guest programs.
 29. The article of manufacture of claim 23, wherein the logic to aggregate for a notification in the list comprises logic to add the notification to the list responsive to an indication by the hypervisor specifying involvement in processing an I/O interruption associated with that notification.
 30. The article of manufacture of claim 29, wherein the indication is provided in a control associated with a guest program corresponding to the I/O interruption.
 31. An article of manufacture comprising: at least one computer usable medium having computer readable program code logic to manage input/output (I/O) interruptions, the computer readable program code logic comprising: logic to obtain an I/O interruption for a guest program of a virtualized real memory environment; logic to determine a dispatch state of the guest program; logic to provide the I/O interruption to the guest program absent intervention by a hypervisor of the virtualized real memory environment, in response to the dispatch state being of one state; and logic to provide the I/O interruption to the guest program with hypervisor intervention, in response to the dispatch state being of another state. 